System and method to anonymize data transmitted to a destination computing device

ABSTRACT

A method and system for anonymizing data to be transmitted to a destination computing device is disclosed. Anonymization strategy for data anonymization is provided. Data to be transmitted is received from a user computer. The data includes a plurality of numbers and defines a clear data in a first base encoding scheme, with one or more predefined characteristics. The clear data is converted to a modified clear data in a second base encoding scheme. The modified clear data is anonymized using an anonymization module, to derive an interim anonymized data in the second base encoding scheme. A converted interim anoymized data in the first base encoding scheme is designated as the anonymized data, if the converted interim anonymized data meets the predefined characteristics of the clear data. The anonymized data is transmitted to the destination computer over a network.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of application Ser. No. 13/929,784 filed on Jun. 28, 2013, which is a continuation-in-part of application Ser. No. 13/844,509 filed on Mar. 15, 2013, which is a continuation-in-part of a) application Ser. No. 13/042,459 filed on Mar. 8, 2011 and b) application Ser. No. 13/323,821 filed on Dec. 13, 2011. Application Ser. Nos. 13/929,784, 13/844,509, 13/042,459 and 13/323,821 are all incorporated herein by reference, in their entirety.

TECHNICAL FIELD

The present invention relates generally to transmitting data to and retrieving data from a destination computing device and particularly, to anonymize data transmitted to the destination computing device and de-anonymize data retrieved from the destination computing device.

DESCRIPTION OF RELATED ART

The Internet has enabled computer users all over the world to interact, communicate, store and access information electronically. One particularly popular mode for running applications over the internet is to host application on a server located in a remote location, along with data associated with the applications. The users of the application access the application and associated data over the internet. Sometimes, this mode of running applications in a remote location is referred to as cloud computing. It is not uncommon for the application to be hosted on a server owned or controlled by a third party. And, various clients or users of the application run the application hosted on the server at the third party location and store data corresponding to the application on a data storage device, for example, a database running on a computing device at the third party location.

There are multiple benefits of using a third party hosted application to a client. For example, the application may be managed by subject matter experts who are familiar with the application, for example a customer relationship management (CRM) application. Sometimes, ancillary applications and resources needed to provide best in class application may be made available to all the clients of the application. The third party may be able to allocate resources based on varying or seasonal demands of each of its customers.

As more and more enterprises or customers use applications hosted at third party locations, the data associated with the enterprise may need to be protected from unauthorized access. Some of the data security requirements may be imposed by regulatory bodies. Some of the data security requirement may be client specific.

As more and more applications are hosted at the third party locations and corresponding data is stored at the third party locations, there is a need to find efficient ways to provide data security to the data stored at the third party locations. With these needs in mind, the current disclosure arises. This brief summary has been provided so that the nature of the disclosure may be understood quickly. A more complete understanding of the disclosure can be obtained by reference to the following detailed description of the various embodiments thereof in connection with the attached drawings.

SUMMARY OF THE INVENTION

In one embodiment, a method for anonymizing data to be transmitted to a destination computing device is disclosed. Data to be transmitted is received from a user computer. The data includes a plurality of numbers and defines a clear data in a first base encoding scheme, with one or more predefined characteristics. The clear data is converted to a modified clear data in a second base encoding scheme. The modified clear data is anonymized using an anonymization module, to derive an interim anonymized data in the second base encoding scheme. A converted interim anoymized data in the first base encoding scheme is designated as the anonymized data, if the converted interim anonymized data meets the predefined characteristics of the clear data. The anonymized data is transmitted to the destination computer over a network.

In yet another embodiment, an anonymization system to anonymize data transmitted to a destination computing device is disclosed. The system includes an anonymization strategy module to store anonymization strategy for data anonymization, wherein the data includes a plurality of numbers and defines a clear data in a first base encoding scheme, with one or more predefined characteristics. The system further includes a logic to convert the clear data to a modified clear data in a second base encoding scheme. The modified clear data is anonymized using an anonymization module, to derive an interim anonymized data in the second base encoding scheme. A converted interim anoymized data in the first base encoding scheme is designated as the anonymized data, if the converted interim anonymized data meets the predefined characteristics of the clear data. The anonymized data is transmitted to the destination computer over a network.

This brief summary has been provided so that the nature of the disclosure may be understood quickly. A more complete understanding of the disclosure can be obtained by reference to the following detailed description of the preferred embodiments thereof in connection with the attached drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other features of several embodiments are now described with reference to the drawings. In the drawings, the same components have the same reference numerals. The illustrated embodiments are intended to illustrate but not limit the invention. The drawings include the following Figures:

FIG. 1A shows a block diagram of a system with anonymization system of the present disclosure used to process requests from a user system to an application server, according to one aspect of the present disclosure;

FIG. 1B shows a block diagram of the user system of FIG. 1 configured to communicate with a server over the network, according to one aspect of the present disclosure;

FIG. 2 shows a block diagram of the internal functional architecture of a user computer, according to one aspect of the present disclosure;

FIG. 2A shows a block diagram of another embodiment of a system used to service requests from a user computer, according to another aspect of the present disclosure;

FIG. 3 shows an exemplary topology of computer network coupling user computers to servers over the internet, according to one aspect of the present disclosure;

FIGS. 4 and 4A show an exemplary block diagram of an anonymization system, according to one aspect of the present disclosure;

FIG. 5 shows an exemplary anonymization strategy data table, according to one aspect of the present invention;

FIG. 6A shows an exemplary block diagram of a searchable encryption system, according to one aspect of the present disclosure;

FIG. 6B shows an exemplary table 620 showing various iterations of the encoding operation of the searchable encryption system of FIG. 6A, according to one aspect of the present disclosure.

FIG. 6C shows an exemplary table 650 showing various iterations of the decoding operation of the searchable encryption system of FIG. 6A, according to one aspect of the present disclosure.

FIG. 7A shows an exemplary crypto module, according to one aspect of the present disclosure;

FIG. 7B shows a table that describes an exemplary relationship between seed value ID, seed value and initialization vector, according to one aspect of the present disclosure;

FIG. 7C shows exemplary data fields for seed value ID and anonymized data, according to one aspect of the present disclosure;

FIG. 7D shows exemplary data fields for seed value ID, order indicator data and anonymized data, according to one aspect of the present disclosure.

FIG. 7E shows an exemplary table showing a portion of the received data, corresponding order indicator data, seed value ID and corresponding anonymized data, according to one aspect of the present disclosure.

FIG. 7F shows an exemplary order indicator generator, according to one aspect of the present disclosure.

FIG. 7G shows an exemplary table showing the received data, corresponding anonymized data and search ID field data, according to one aspect of the present disclosure.

FIG. 7H shows an exemplary table showing search keys and corresponding search IDs, according to one aspect of the present disclosure.

FIG. 7J shows an exemplary anonymized data with a search ID indicator and search ID field.

FIG. 7K shows an exemplary clear data, modified clear data, interim anonymized data, converted interim anonymized data and interim anonymized clear data fields.

FIG. 7L shows an exemplary logic module with a conversion module, manipulation module and comparison module.

FIGS. 8A-8D shows exemplary anonymization of data transmitted to a destination computing device;

FIGS. 9A-9C shows exemplary de-anomymization of data received from the destination computing device;

FIG. 10 shows method of anonymizing data to be transmitted to a destination computing, according to one aspect of the present disclosure;

FIG. 11A shows method of processing a request for stored anonymized data by the destination computing device; and

FIG. 11B shows method of processing selectively retrieved anonymized data from the destination computing device.

DETAILED DESCRIPTION

To facilitate an understanding of the adaptive aspects of the present invention, the general architecture and operation of a networked system is described. The specific architecture and operation of the adaptive aspects of the present disclosure are then described with reference to the general architecture.

FIG. 1A shows a top-level block diagram of a system 100 with anonymization system of this disclosure that is used to send data from a user system, according to one aspect of the present disclosure. System 100 includes a user system 102 that is coupled via a gateway 104 and a network connection 106 to a server 110 through another gateway 108. In one aspect, server 110 is a web-server. Gateway 104 in one embodiment includes an anonymization system 112 of this disclosure. Database 114 is used to store information that is accessed by the user system 102. In one aspect, database 114 is a structured query language (SQL) based database.

FIG. 1B is a block diagram of a user system 102 according to one embodiment of the present disclosure, which is configured to communicate with the server 110 over the network. FIG. 1B includes a user computer 116 (sometimes referred to as computer 116) and a monitor 118. Monitor 118 may be a CRT type, a LCD type, a plasma type, or any other type of color or monochrome display. Also provided with computer 116 is a keyboard 120 for entering text data and user commands, and a pointing device 122 (such as a mouse) for processing objects displayed on monitor 118. In some embodiments, objects displayed on monitor 118 may be elements of a graphical user interface.

Computer 116 may include a computer-readable memory medium such as a rotating disk 124 for storing readable data. Besides other programs, disk 124 can store application programs including web browsers by which computer 116 connects to a network and the systems described below, according to one aspect of the present disclosure. In some embodiments, disk 124 may be a disk system with a plurality of disk drives arranged as a Redundant Array of Inexpensive Drives (RAID) system, accessible using a storage adapter (not shown).

Computer 116 can also access a computer-readable storage device 126 with removable storage media storing data files, application program files, and computer executable process steps embodying the present invention or the like. For example, the storage device 126 may be a CD-ROM or a DVD ROM. In some embodiments, the storage device 126 may support removable storage media that is read-only device (R), write once-read many (WORM), or rewriteable (RW) type. In some embodiments, the storage device 126 may also be provided with computer 116 to access application program files, audio files and data files stored on a removable storage media. In some embodiments, the removable storage media may be optical, magnetic, magneto-optic, or semiconductor based recording media.

A modem, an integrated services digital network (ISDN) connection, wireless or the like also provides computer 116 with a DSL/Cable/satellite/wireless (or Internet connection) 128 to the World Wide Web (WWW). Internet connection 128 allows computer 116 to send and receive commands, data files, audio files, application program files and computer-executable process steps embodying the present invention.

Computer 116 is also provided with external audio speakers 130A and 130B to assist a listener to listen to music either downloaded on-line from the Internet or off-line using a storage medium. It is noteworthy that a listener may use headphones instead of audio speakers 130A and 130B to listen to music.

FIG. 2 is a block diagram showing the internal functional architecture of computer 116. As shown in FIG. 2, computer 116 includes a central processing unit (CPU) 201 for executing computer-executable process steps and interfaces with a computer bus 208. Also shown in FIG. 2 are a WWW interface 202, a display device interface 203, a keyboard interface 204, a pointing device interface 205, an audio interface 209, video interface 210, printer interface 212, and a disk 124. Audio Interface 209 allows a listener to listen to music, Online (downloaded using the Internet or a private network) or offline (using a CD).

As described above, disk 124 may store operating system program files, application program files, web browsers, and other files. Some of these files are stored on disk 124 using an installation program. For example, CPU 201 executes computer-executable process steps of an installation program so that CPU 201 can properly execute the application program.

A random access main memory (“RAM”) 206 also interfaces to computer bus 208 to provide CPU 201 with access to memory storage. When executing stored computer-executable process steps from disk 124 (or other storage device such as storage device 126 or Internet connection 128), CPU 201 stores and executes the process steps out of RAM 206.

Read only memory (“ROM”) 207 is provided to store invariant instruction sequences such as start-up instruction sequences or basic input/output operating system (BIOS) sequences for operation of keyboard 120.

FIG. 2A shows yet another example of the overall system 100, according to one aspect of the present disclosure. In FIG. 2A, server 110 is shown as a web server and database 114 is shown as a SQL (structured query language) database. FIG. 2A also shows the various steps that are used to access database 114. In step 1, a user using a browser running on the user system 102, submits a URL, as a request. URL includes the application to which the request is directed. In step 2, the web server 110 captures the request, and locates and executes corresponding application specific program (ASP) code for the application to which the request was directed.

In step 3, during execution of ASP code, a structured query language (SQL) code is generated and executed. Based on the executed SQL code, database 114 is accessed to fetch, add, modify or delete information in the database.

In step 4, the results are sent to the web server 110. The web server 110 constructs a response, for example as a HTML code. In step 5, HTML code is sent to the user system 102. In step 6, the HTML page is sent to the browser and displayed on the user system 102.

Although in this example, a user submits a URL as a request, in some embodiments, a user application executing on the user computer 102 may submit a request. The request may be submitted as a URL, and the user application may be configured to receive the response to the request.

Now, an exemplary coupling of the computer 116 to a server over the internet will be described with reference to FIG. 3. FIG. 3 shows an exemplary topology of a computer network with computers similar to computer 116, connected to the Internet 302. For illustration purposes, three computers X, Y and Z are shown connected to the Internet 302 via Web interface 202 through a gateway 301, where gateway 301 can interface N number of computers. Gateway 301 may be similar to gateway 104 with an anonymization system 112. Web interface 202 may be a modem, network interface card or a unit for providing connectivity to other computer systems over a network using protocols such as X.25, Ethernet or TCP/IP, or any device that allows, directly or indirectly, computer-to-computer communications. Gateway 301 and computers X, Y and Z may be located or controlled within a user controlled environment. This user controlled environment may be within the user controlled enterprise or intranet. For convenience, gateway 301 and computers X, Y and Z are grouped together and referred to as user cloud 309. Exemplary topology of a computer network may have additional groups of computers with gateway to define additional user clouds. In one embodiment, data flow outside the user cloud may need special handling.

It is noteworthy that the invention is not limited to a particular number of computers. Any number of computers can be connected to the Internet 302 or any other computer network may be used.

FIG. 3 further shows a second gateway 303 that connects a network of web servers 304 and 305 to the Internet 302. Web servers 304 and 305 may be connected with each other over a computer network. Web servers 304 and 305 receive requests from the user computer and respond to the requests received from the user computer. Web server 304 is coupled to a database 306 and web server 305 is coupled to a database 307. In one embodiment, the web server may be hosting an application for use by the user computer. As an example, web server 304 is hosting server application SA0 and web server 305 is hosting server application SA1. As one skilled in the art appreciates, server applications may be a hosted customer relationship management software (CRM) application, a website, online shop, news service, search applications, social networking applications, blog sites, webmail and the like.

In one embodiment, the gateway 303, servers 304 and 305, and databases 306 and 307 may be hosted at a third party location. For convenience, gateway 303, servers 304 and 305, and databases 306 and 307 are grouped together and referred to as hosted cloud 310. Exemplary topology of a computer network may have additional groups of servers with gateways and databases to define additional hosted clouds.

The following provides a brief description of the Internet. The Internet connects thousands of computers world wide through well-known protocols, for example, Transmission Control Protocol (TCP)/Internet Protocol (IP), into a vast network. Information on the Internet is stored world wide as computer files, mostly written in the Hypertext Mark Up Language (“HTML”). Other mark up languages, e.g., Extensible Markup Language (“XML”) as published by W3C Consortium, Version 1, Second Edition, October 2000, ©W3C may also be used. The collection of all such publicly available computer files is known as the World Wide Web (WWW). The WWW is a multimedia-enabled hypertext system used for navigating the Internet and is made up of hundreds of thousands of web pages with images and text and video files, which can be displayed on a computer monitor. Each web page can have connections to other pages, which may be located on any computer connected to the Internet.

A typical Internet user uses a client program called a “Web Browser” to connect to the Internet. A web browser is a software program that allows users to access the content stored in Web sites. Modern Web browsers can also create content “on the fly”, according to instructions received from a Web site. This concept is commonly referred to as “dynamic page generation”. In addition, browsers can commonly send information back to the Web site, thus enabling two-way communication of the user and the Web site. A user can connect to the Internet via a proprietary network, such as America Online, or via an Internet Service Provider, e.g., Earthlink. The web browser may run on any computer connected to the Internet. Currently, various browsers are available of which two prominent browsers are Microsoft Internet Explorer and Mozilla Firefox. The Web Browser receives and sends requests to a web server and acquires information from the WWW. A web server is a program that, upon receipt of a request, sends the requested data to the requesting user. A standard naming convention known as Uniform Resource Locator (“URL”) has been adopted to represent hypermedia links and links to network services. Most files or services can be represented with a URL.

URLs enable Web Browsers to go directly to any file held on any WWW server. Information from the WWW is accessed using well-known protocols, including the Hypertext Transport Protocol (“HTTP”), the Wide Area Information Service (“WAIS”) and the File Transport Protocol (“FTP”), over TCP/IP protocol. The transfer format for standard WWW pages is Hypertext Transfer Protocol (HTTP).

Web domain is an Internet address that provides connection to a Web server. Generally, URLs have three parts: the first part describes the protocol used to access the content pointed to by the URL, the second contains the directory in which the content is located, and the third contains the file that stores the content: <protocol>:<domain><directory><file>.

For example:

http://www.ciphercloud.com/bios.html

http://www.ciphercloud.com/index.html

http://fn.cnn.com/archives/may2009/pr3.html

ftp://userl.ciphercloud.com/software/pages.zip

Commonly, the <protocol> part may be missing. In that case, modern Web browsers access the URL as if the http://prefix was used. In addition, the <file> part may be missing. In that case, one of the convention calls for the file “index.html” to be fetched. In some cases, the request may be redirected to fetch another default file.

For example, the following are legal variations of the previous example URLs:

www.ciphercloud.com/bios.html

www.ciphercloud.com

fn.cnn.com/archives/may2009/pr3.html

ftp://userl.ciphercloud.com/software/pages.zip Web Page.

Web page is the content associated with a URL. In its simplest form, this content is static text, which is stored into a text file indicated by the URL. However, very often, the content contains multi-media elements (e.g. images, audio, video, etc) as well as non-static text or other elements (e.g. news tickers, frames, scripts, streaming graphics, etc). Very often, more than one file forms a Web page. However, there is only one file that is associated with the URL and which initiates or guides the Web page generation.

When a Web browser receives an URL, the Web browser requests a Domain Name System (DNS) name server to decode the domain name and return the IP address for the domain name. The DNS name server returns the IP address of the domain name as stored in the DNS name server to the web browser. Web browser uses the IP address for the domain name and sends a request corresponding to the requested URL that confirms to the HTTP protocol to the IP address. In one embodiment, the request is sent using TCP/IP protocol over the internet.

In one embodiment, the user computer 116 sends requests to the server using HTTP protocol. As previously described with reference to FIG. 2A, the request is processed by the web server and a response is sent to the user computer. In the exemplary topology described with reference to FIG. 3, the request is sent over the internet to the server. In some embodiment, requests may be sent using Hypertext Transfer Protocol Secure (HTTPS) protocol, which is a combination of HTTP protocol with SSL/TLS protocol to provide encrypted communication and secure identification of a network web server.

Now, one embodiment of an anonymization system 402 is described with reference to FIG. 4. Anonymization system 402 may be similar to anonymization system 112. FIG. 4 shows the anonymization system 402 as part of gateway 400 that connects to the network, but the anonymization system 402 can be provided in other ways, such as software running on a server, distributed software, or various software and hardware packages operating together. In one embodiment, the anonymization system 402 may be part of the gateway described with reference to FIG. 1A and FIG. 3. The gateway 400 is configured to communicate with the user systems within the user cloud and communicate with the hosted cloud over the network. The anonymization system 402 will be described in detail, with reference to FIG. 4A.

Now referring to FIG. 4A, the anonymization system 402 includes a management console module 404, an anonymization strategy module 406, anonymization module 408, de-anonymization module 410, tokenization module 412 and one or more crypto modules, shown as crypto 1 module 416, crypto 2 module 418 and crypto N module 420. Additionally, a token vault 414 is also part of the anonymization system 402. As one skilled in the art appreciates, various modules referenced in this disclosure may be implemented in hardware, software executed on a computing device or a combination of hardware and software. Additionally, various modules may be implemented as an integrated unit or may be implemented as separate functional units that interact with each other using a communication protocol.

The management console module 404 is configured to communicate with various applications running on the hosted cloud, over the network. Additionally, the management console module 404 is also configured to communicate with the user computer. For example, the management console module 404 may send queries to various applications running on the hosted cloud and receive meta data (or data schema, data definitions) of each application.

The management console module 404 may also present the received meta data information about the applications running on the hosted cloud to the user. The management console module 404 may additionally present the available anonymization strategies for each data field of the meta data to the user computer. The user may select one or more of the anonymization strategies to be applied to various data fields of the application, using the user computer.

The selected anonymization strategy is stored by the management console module 404 in the anonymization strategy module 406, for later use by other modules of the anonymization system 402. The anonymization strategy may be stored as a table in the anonymization strategy module 406. The anaonymization strategy in one embodiment may include schema definition for data manipulation. An exemplary selected anonymization strategy will be described later with reference to FIG. 5.

The anonymization module 408 is configured to intercept any data to be transmitted from a user computer to the hosted cloud. The anonymization module 408 is also configured to communicate with the anonymization strategy module 406 and evaluate various fields of data to be transmitted against anonymization strategy stored in the anonymization strategy module 406. Based upon this evaluation, the anonymization module 408 is configured to perform anonymization of one or more data fields using one or more of the tokenization module 412 and crypto modules, for example, crypto 1 module 416 and crypto 2 module 418 and generate corresponding anonymized data field.

The anonymization module 408 is also configured to reassemble the data to be transmitted to the hosted cloud, using the anonymized data fields. In one embodiment, the reassembled data includes one or more unique data pattern added to the anonymized data fields to indicate the selected anonymization strategy used to anonymize the data fields. In one embodiment, a preamble is appended to the beginning of the anonymized data field. In one embodiment, a postamble is appended to the end of the anonymized data field. The reassembled data is forwarded to the hosted cloud over the network using the gateway 400. Various functions and features of the tokenization module 412 and crypto modules will be described later.

The de-anonymization module 410 is configured to intercept any data received by the user computer from the hosted cloud. The de-anonymization module 408 is also configured to evaluate various fields of data received from the hosted cloud to detect and decode the preamble and postamble of the data fields. Based upon this evaluation, the de-anonymization module 410 is configured to perform de-anonymization of one or more data fields using one or more of the tokenization module 412 and crypto modules, for example, crypto 1 module 416 and crypto 2 module 418 and generate corresponding de-anonymized data field. The de-anonymization module 410 is also configured to reassemble the data to be transmitted to the user computer, using the de-anonymized data fields. The reassembled data is forwarded to the user computer.

Now, referring to FIG. 5, an exemplary anonymization strategy data table 500 for server application SA0 stored by the anonymization strategy module 406 is described. As one skilled in the art appreciates, the anonymization strategy data may be stored in other forms other than a table form. Column 502 shows various data fields of server application SA0. Each of the rows of table 500 shows the data field and their corresponding characteristics. As an example, Column 504 shows data type for each of the data fields, for example numeric, alphabetical or alpha-numeric characters. Column 506 shows the length of the data field. Column 508 shows whether any portion of the data field needs to be retained as originally provided by the user computer. Column 510 shows the selected anonymization strategy for each of the data fields.

Now referring to row 512, various attributes of DATA FIELD 1 is stored in table 500. For example, DATA FIELD 1 is a numeric field of length 10 characters. Characters 8 through 10 of DATA FIELD 1 needs to be retained in its original form. The selected anonymization strategy for DATA FIELD 1 is TPF1. For example, DATA FIELD 1 may be a telephone number and characters 10:08 may represent the area code of the telephone number and may have to be maintained in its original form at the hosted cloud. However, characters 07:01 will be anonymized using anonymization strategy TPF1. In one embodiment, TPF1 may correspond to anonymization using tokenization module 412. In one embodiment, TPF1 may correspond to anonymization using Crypo 1 module 416. In one embodiment, a preamble indicative of TPF1 anonymization strategy may be appended to the anonymized DATA FIELD 1.

Now referring to row 514, various attributes of DATA FIELD 4 is stored in table 500. For example, DATA FIELD 4 is an alphabetic field of length 8 characters. No characters need to be retained in its original form. The selected anonymization strategy for DATA FIELD 4 is TRF4. In one embodiment, TRF4 may correspond to anonymization using crypto 2 module 418. In one embodiment, TRF4 may correspond to anonymization using crypto N module 420. In one embodiment, a preamble indicative of TRF4 anonymization strategy may be appended to the anonymized DATA FIELD 4.

Now referring to row 516, various attributes of DATA FIELD 8 is stored in table 500. For example, DATA FIELD 8 is an alpha-numeric field of length 24 characters. No characters need to be retained in its original form. The selected anonymization strategy for DATA FIELD 8 is none. Based on this selection, no anonymization of DATA FIELD 8 will be performed and the data contained in DATA FIELD 8 will be sent in its original form.

Now various anonymization techniques implemented in various anonymization modules like tokenization module 412 and crypto modules like crypto 1 module, crypto 2 module and the like will be described. The anonymization technique selected for a data field may be based upon multiple factors. One of the factors is level of desired security. One of the other factors is data attribute preservation for the data field. The data attribute preservation refers to retaining capabilities to perform operations on the stored data field in their anonymized form as compared to the stored data in its original or clear form. Some of the operations that may be performed on the stored data field in their anonymized form include sorting in the order of their clear data form (or original data form), searching, searching regardless of the case of the characters, searching using partial string match or wild card match. As one skilled in the art appreciates, as more data attributes are preserved in the stored data form, in some embodiments, it may lead to decreased level of data security. Clear data or original data refers to the data as present in the data field before anonymization.

Anonymization techniques may be broadly divided into two categories. One, a token based anonymization. The token based anonymization may be implemented in the tokenization module 412 and may require local storage of the tokens in the token vault 414. Another technique is to use a symmetric key encryption based anonymization. Symmetric key encryption based anonymization technique may be implemented in one or more of the crypto modules, for example, crypto module 1, crypto module 2 and the like. Now, various anonymization techniques for each of the token based anonymization and symmetric key encryption based techniques will be described.

Token Based Anonymization Techniques:

Random token anonymization: In this technique, for data contained in each data field, a corresponding token is created. The token vault 414 is used to store the relationship between the original or clear data and the corresponding token. The token is sent to the hosted cloud, after prepending a preamble indicative of the type of anonymization performed on the data field. When the data field is retrieved from the hosted cloud, based on the preamble indicative of the type of anonymization performed, the token is used to extract the corresponding clear data stored in the token vault 414. The de-anonymized data is then forwarded to the user computer.

Sortable token anonymization: In this technique, the token vault is organized in a balanced, ordered tree, with each node representing a specific token that corresponds to a specific clear data. For an input data, the tokenization module 412 looks up the tree in the token vault 414 for a node that has not been used for clear data corresponding to the input data and establish a new token that corresponds to the input data. The new token is mapped to the input data. The new token in the selected node maintains the order of the tree. In this way, the token continues to maintain the order that corresponds to the original or clear data. The order may correspond to the position, sequence, or value of the original data. For example, the order may be based on alphabetical sequence, numerical sequence, value of the characters based on an assigned value or value of the characters based on a pre-assigned value, for example, Unicode value. The new token is then sent to the hosted cloud.

Token anonymization that allows case-insensitive search: In one embodiment, for each data, two tokens are generated. One, based on the original or clear form of the data and the other based on all lower cases. In one embodiment, random token anonymization technique is used, as described above. Both of the generated tokens are sent to the hosted cloud, with the token corresponding to all lower case is stored in a hidden field in the application.

When a search request is received for this field from the user computer, for example, as a keyword in clear form, search request is generated by the anonymization system 402, for both the clear form and all lower case. For example, anonymized keywords are generated, one based on the keyword in its original form and another based on keyword with all lower cases. The search request is then sent to the host cloud, with anonymized keyword for both clear form and all lower case. In one embodiment, the search request is sent with an “OR” logic so as to receive search results for both the keywords. Any results of the search received from the host cloud for both the anonymized keyword for clear form and anonymized keyword for all lower case will then be de-anonymized by the de-anomymization module of the anonymization system. The de-anonymized results are then presented to the user computer. As one skilled in the art appreciates, a keyword received in a search request may be full data field, few characters of a data field or few characters with a wild card. Principles described herein will work for all of these cases, as the search request sent to the host cloud will be based on anonymized keyword.

Symmetric key encryption techniques:

AES encryption per word, with hard coded salt: In this technique, the data field values are broken down into words. Each of the word is encrypted using AES encryption using a hard coded salt. This technique will generate same encrypted data for the same input data, for each encryption cycle. The encrypted data is stored in the hosted cloud. A search word for exact match may be issued by the user computer to the hosted cloud. Corresponding encrypted data for the search word is generated by the anonymization system and sent to the hosted cloud. Any hits for exact match is returned to the anonymization system by the hosted cloud. The hits for exact match are then de-anonymized by the de-anonymization module 410 and presented to the user computer.

AES encryption per word, with hard coded salt that allows case-insensitive search: In one embodiment, for each word, two encrypted data words are generated. One, based on the original or clear form of the data word and the other based on all lower case of the data word. In one embodiment, AES encryption with hardcoded salt anonymization technique is used, as described above. Both of the generated anonymized data are sent to the hosted cloud, with the anonymized data corresponding to all lower case is stored in a hidden field in the application. When a search request is received for this field from the user computer, search request is generated by the anonymization system 402, for both the anonymized data words and sent to the host cloud. In one embodiment, the search request is sent with an “OR” logic so as to receive search results for both the encrypted words. Any results of the search received from the host cloud by the anonymization system will then be de-anonymized and presented to the user computer.

Searchable encryption: In this technique, encryption algorithm is designed to encrypt words of text. The encrypted values preserve the properties of sorting and equality of the clear values. As an example, the equality can be either case-sensitive or case-insensitive. As another example, sorting may be either case-sensitive or case-insensitive. In one embodiment, accented characters may be treated as equal characters. i.e. a character “E” and “É” may be treated as equal or same. In one embodiment, accented characters may be treated as adjacent characters, with “É” positioned after “E”. Some of these techniques may permit both order preserving property for the anonymized data and case-insensitive search capability. Exemplary searchable encryption to encode words of a text will now be described with reference to FIGS. 6A-6B.

FIG. 6A shows an exemplary block diagram of a searchable encryption system 600. The searchable encryption system 600 may be implemented in the anonymization system 402. The searchable encryption system 600 includes an input logic 602 to receive input word to be encrypted, an encryption engine 604, a compare logic 606 and an encode logic 608. Various elements of the encryption system 600 may be implemented in various functional modules of the anonymization system 402, for example, in the anonymization module 408, crypto modules 416-418, de-anonymization module 410 and the like. For example, the encryption engine 604 may be part of one of the crypto modules 416-420.

The input logic 602 is configured to receive the input word to be fed to the encryption engine 604. In one embodiment, the encryption engine 604 receives each of the characters of the input word and generate a random character as an output. The encryption engine 604 may include a Pseudo-Random Number Generation Algorithm (PRNG) to generate a random character as an output. The PRNG is preferably secure and is fast. One exemplary PRNG may be a RC4 cipher. In one embodiment, the generated random character will be within a predefined range of characters, which narrows in subsequent iterations, as will be described later.

The output of the encryption engine 604 is fed to the compare logic 606. The compare logic 606 is also configured to receive the corresponding input character as an input. The compare logic 606 is configured to compare generated output character of the encryption engine 604 with the corresponding input character in a first range of characters and generate a binary bit, based on whether the input character is higher in position or lower in position relative to the generated output character. As an example, a bit 0 is generated if the position is lower and a bit 1 is generated, if the position is higher relative to the generated output character. The generated output character is now fed as input to the encryption engine 604 to generate a second generated output character, within a second range of characters.

The second generated output character is again compared with the input character by the compare logic 606 and generate next bit of output based on the position of the input character relative to the second generated output character, within the second range of characters (which is smaller than the first range). The operation is repeated to generate additional output bits until the range is such that there are only two characters before or after the input character. Now, the next character of the input word is processed to generate second set of output bits. This operation will be further described with reference to FIG. 6B with table 620.

Referring to FIG. 6B, table 620 shows for each iteration in column 622, the corresponding character range in column 624 and the output of the compare logic for each iteration in column 626. For simplicity, only words with uppercase characters will be described. For example, if the word to be encoded is “GOLD”, initial encoding starts with encoding the first character “G”. The character G is fed to the encryption logic 604 as a first input character and the encryption logic 604 is configured to generate a random character as an output, for example, a random character between A-Z, which defines the first range of characters. Let us assume, the first generated random character output is Q.

Now, the first input character “G” is compared with the first generated random character output “Q” by the compare logic 606 to see if it is higher in position or lower in position relative to the first generated random character output, within the range shown in cell 628 which corresponds to the first iteration 630. In this case, as character G is lower in position to the first generated random character output Q, a binary value of “0” is output as the first bit of the encoded data, as shown in cell 632. Additionally, the first generated random character output Q defines the upper bound (as character Q is higher in position relative to character G) for the range of characters to be used in the next iteration, for example, second range of characters A-Q.

Next, the first generated random character output (in this case character “Q”) is input to the encryption logic 604 and the encryption logic outputs a second generated random character output, within the second range of characters, as shown in cell 634. As one skilled in the art appreciates, the second range of characters is A-Q and the range of characters the encryption logic can output will be configured to be between A-Q. Let us assume, the second generated random character is character “C”.

Now, the first input character is again compared with the second generated random character output to see if it is higher in position or lower in position relative to the second generated random character output. In this case, as character G is higher in position to the second generated random character output C, a binary value of “1” is output as the second bit of the encoded data, as shown in cell 636. Additionally, the second generated random character output C defines the lower bound (as character C is lower in position relative to character G) for the range of characters to be used in the next iteration, for example, third range of characters C-Q.

Now, the second generated random character output C is input to the encryption engine 604 and the encryption engine 604 outputs a third generated random character output. In this case, the third range of characters the encryption engine 604 can output is be configured to be within the third range of characters C-Q. Let us assume, the third generated random character is character “E”, with a “1” assigned to the third bit of the encoded data, based on the comparison. Additionally, the third generated random character output E defines the lower bound (as character E is lower in position relative to character G) for the range of characters to be used in the next iteration, for example, fourth range of characters E-Q.

Similarly, referring to iteration 4, fourth generated random character is character “J” with an output of “0” as the forth bit of the encoded data, based on the comparison. Additionally, the fourth generated random character output J defines the upper bound (as character J is higher in position relative to character G) for the range of characters to be used in the next iteration, for example, fifth range of characters E-J.

Similarly, referring to iteration 5, the fifth generated random character is character “H”, with a “0” assigned to the fifth bit of the encoded data, based on the comparison. This process is repeated until there are two or less characters left before and after the first input character, at which time, the encoding stops. So, in this case, as there are only two characters E and F before and one character J after the first input character G, the encoding stops. So, the final encoded output for character “G” is “00110”.

The rest of the characters “0”, “L” and “D” are similarly processed to get their corresponding encoded output. As an example, let the final encoded output for “GOLD” is 010010001010010100000110. As one skilled in the art appreciates, depending upon the random character generated by the encryption engine 604, each character may have different number of bits as their encoded output. Now the final encoded output is transformed into a character representation, using an encode logic 608, which will be described now.

In one embodiment, the character representation of the final encoded output is done by splitting the final encoded output into a plurality of bits of data and assigning a unique character to each unique combination of a plurality of bits. As an example, four bits may be used to represent 16 different unique combinations, with each combination assigned a specific character. For example, a base-16 encoding may be used and sixteen characters, characters B-Q assigned to the base-16 encoded data. As an example, 0000 may be encoded as character B and 1111 may be encoded as character Q. With base-16 encoding, other characters may be available for assignment for special purposes or for padding. Other random assignments of characters to the base-16 encoded data are also possible. In some embodiments, dummy characters may be padded in the beginning and the end of the range, so that a lowest character in the character range will not encode as all zeros and highest character in the character range will not encode as all ones.

In one embodiment, in order to provide case insensitive search capability, the encoded output is mapped into lower-case characters, for example, characters b-q. Then, specific characters of the mapped word is capitalized, based on the capitalization of the original input word. For example, if the input word was Mom, and the final output is mapped into character combination “def”, then, based on the capitalization of the original input word, the mapped character combination is modified to be “Def”. A case sensitive and a case insensitive search on “mom” would return the appropriate results.

In some situations, the final encoded output may result in a mapped word that may have less characters than the original input word. As an example, for a three character input word, the encoded output may only generate two mapped characters. In such a situation, at least one character that is not used in the output mapping (as only 16 characters are used in a base-16 encoding) may be used as a padding character. Preferably, the padding character should sort before all other used characters. As an example, if the characters B-Q are used for mapping, character A may be used as a padding character to be added to the mapped characters. Character A would sort before the characters B-Q.

As an example, if the input of Mom mapped into “De”, then with the added padding, the modified mapped characters will be Dea, which will have the same number of characters as the original input character. If the original input was “moM” and the input mapped into “De”, then the modified mapped characters will be “deA”, which preserves both the number of characters of the original input and the case of the characters of the original input.

In the above examples, only characters A-Z were considered. In order to expand the search and sortable encryption capabilities to characters outside the A-Z range, one or more escape characters may be pre-pended and/or post-pended to the input word. The escape character may indicate the characteristics of the word being encrypted. As an example, unique escape characters may be pre-pended to the input word to indicate if the input word is a character less than the number “0”, numbers between 0-9, numbers greater than 9 but less than A, letters A-Z, single byte character greater than “Z”, Unicode character in the range U+0080 to U+00FF, Unicode character in the range U+0100 to U+FFFF, Unicode character in the range U+10000 to U+10FFFF and the like. Additionally, a unique escape character may be post-pended to the input word to indicate “end of word”.

As one skilled in the art appreciates, in one embodiment, the searchable encryption system 600 may additionally have a decode logic 612 to receive the encoded word 614 and output the decoded word character string. The decode logic 612 would receive the encoded characters of the encoded word as an input, perform the manipulation necessary to decode the encoded characters one character at a time and reassemble the encoded word as a decoded word. An exemplary decoding operation will be further described with reference to FIG. 6C with table 650.

Referring to FIG. 6C, table 650 shows for each iteration in column 652, the input bit 654 from the encoded word, corresponding character range in column 656. For simplicity, only decoding of character “G” of the encoded word will be described. For example, the character “G” was encoded as “00110”. Iteration 0 refers to the initial set up of the range of characters, for example, first range of characters 658, which will be from A-Z. In iteration 1, the input bit is “0” and the input bit “0” is fed to the decode logic 612. The decode logic 612 generates first random range character Q as an output, based on the input bit of “0”. Since input bit was a “0”, character Q defines the upper bound for the next range of characters to be used in the decoding process. Now, the second range of characters 660 is defined to be from A-Q, based on the generated first random range character “Q”.

Next, in iteration 2, next input bit of “1” is input to the decode logic 612. The decode logic 612 generates second random range character C as an output, based on the input bit of “1”. As the input bit was a “1”, character C+1 defines the lower bound for the next range of characters to be used in the decoding process. Now, the third range of characters 662 is defined to be from D-Q, based on the generated second random range character “C”.

Next, in iteration 3, next input bit of “1” is input to the decode logic 612. The decode logic 612 generates third random range character E as an output, based on the input bit of “1”. As the input bit was a “1”, character E+1 defines the lower bound for the next range of characters to be used in the decoding process. Now, the fourth range of characters 664 is defined to be from F-Q, based on the generated third random range character “E”.

Next, in iteration 4, next input bit of “0” is input to the decode logic 612. The decode logic 612 generates fourth random range character J as an output, based on the input bit of “0”. As the input bit was a “0”, character “J” defines the upper bound for the next range of characters to be used in the decoding process. Now, the fifth range of characters 666 is defined to be from F-J, based on the generated fourth random range character “J”.

Next, in iteration 5, next input bit of “0” is input to the decode logic 612. The decode logic 612 generates fifth random range character H as an output, based on the input bit of “0”. As the input bit was a “0”, character “H” defines the upper bound for the next range of characters to be used in the decoding process. Now, the sixth range of characters 668 is defined to be from F-H, based on the generated fifth random range character “H”.

Now, the fifth range of characters 668 is narrowed down to three characters, F, G and H. The middle character “G” is chosen as the decoded character for the encoded input word. Similarly, rest of the encoded input words are decoded to generate the original word “GOLD”.

Randomizing Anonymization:

As previously discussed, in order to generate the same encrypted data, there is a need to use a fixed hard coded salt. In some embodiments, an initialization vector (IV) is used as part of the encryption scheme. As one skilled in the art appreciates, in some embodiments, the fixed hard coded salt may be similar to an initialization vector.

Now, referring to FIG. 7A, an exemplary crypto module 702 is described. Crypto module 702 may be similar to crypto module 420 of anonymization system 402. The crypto module 702 includes a crypto engine 704 that receives the initialization vector 706 from an initialization vector generator 708. The crypto engine 704 also receives a data encryption key 710 from a data encryption key store 712. The crypto engine is also configured to receive the input data 714. The input data 714 is processed by the crypto engine 704, using the data encryption key 710 and the initialization vector 706 to generate the encrypted output data 716.

The initialization vector generator 708 may include a PRNG function module 720. As previously described, a seed 722 is fed to the PRNG function module. Seed 722 may be generated by a seed generator 724. Based on the value of the seed 722, the PRNG function module 720 generates the initialization vector 706. The Initialization vector generator 708, data encryption key store 712 and seed generator 724 may be part of the anonymization system 402.

Now, as an example, let the input data 714 be “xyz” and the encrypted output data 716 be “abc”. For example, the encrypted output data 716 is stored, say in a database. If there is a request to perform a search using the search term “xyz” and retrieve the encrypted output data, the search request sent to the database needs to be modified to include the encrypted output data “abc” as the search term. In order to convert the search term “xyz” to “abc”, the search term “xyz” is fed to the crypto engine 704. We also need to use the same initialization vector 706 value and same data encryption key as originally used. This means, we need to use the same seed value for the seed 722 in order to generate the same initialization vector 706 value. As one skilled in the art appreciates, if the same initialization vector 706 value is used on a regular basis, there is a risk of compromizing the encryption system. In order to minimize the risk of compromising the encryption system, a plurality of initialization vectors are used in the encryption system, as described below.

In some embodiments, a plurality of known seed values are used to generate a plurality of initialization vectors. For example, referring to FIG. 7B, a table 730 shows the relationship between seed value and corresponding initialization vector. For example, column 732 shows the seed value ID, column 734 shows the corresponding seed value and column 736 shows the corresponding generated initialization vector. As an example, referring to row 740, for the seed value ID of SVID-1, the corresponding seed value is SV-1 and the corresponding generated initialization vector is IV-1. Similarly, referring to row 742, for the seed value ID of SVID-2, the corresponding seed value is SV-2 and the corresponding generated initialization vector is IV-2.

During the anonymization process, the system may selectively use different seed values to generate different initialization vector values. During the de-anonymization process, to de-anonymize the anonymized data, there is a need to know the initialization vector that was used to anonymize the input data.

In one embodiment, the seed value ID used to generate the initialization vector is stored along with the anonymized data. For example, referring to FIG. 7C, the seed value ID is stored in field 750 and anonymized data is stored in field 752. Seed value ID along with the anonymized data is sent to the destination computing device. As one skilled in the art appreciates, one or more additional fields may also be added to the data sent to the destination computing device. For example, preamble fields and post amble fields may be added.

When the anonymized data is retrieved along with the seed value ID, the seed value ID is used to determine or fetch the corresponding seed value. This seed value is then used to generate the initialization vector, which will have the same value as the initialization vector that was used to encrypt the input data. This generated initialization vector is then used to de-anonymize the anonymized data.

When there is a need to send a query to be performed on the stored anonymized data, for example, a search or a sort query, there is a need to modify the query such that any field representing a portion of the original data (or clear text) is modified to include a corresponding encrypted data. As an example, if there is a request to perform a search using the search term “xyz” and retrieve the encrypted output data, the search request sent to the database needs to be modified to include the encrypted output data as the search term. If different seed values are used to generate different initialization vector values, then, based on the value of the initialization vector, the encrypted output data will be different.

For example, for seed value corresponding to SVID-1, for an input data of “xyz”, an encrypted output data of “abc” may be generated. And, for a seed value corresponding to SVID-2, for the same input data of “xyz”, an encrypted output data of “efg” may be generated. So, in a system where multiple seed values are used, as an example, for a search query containing input data “xyz”, all possible combination of corresponding encryption data is generated, using different seed values stored in the system.

For example, if the system had only two seed values, then, using the example above, for a search query for input data “xyz”, two possible encrypted data will be generated, namely, “abc”, “efg”. Then, a modified search query is generated with all the possible encrypted data patterns for input data “xyz”. The modified search query is then sent to the database storing the encrypted data, to retrieve the encrypted data corresponding to the plurality of search terms.

The retrieved encrypted data is then decrypted to derive corresponding clear data. Then, the clear data that corresponds to the original query is then sent to the user. As one skilled in the art appreciates, when the clear data is derived from the encrypted data, one or more of the clear data may not correspond to the data requested in the original query, as only one of the plurality of the seed values generated the encrypted data that corresponds to the input data in the query. Those records that do not correspond to the data requested in the original query are just discarded.

As one skilled in the art appreciates, as the number of seed values used to generate the initialization vector is increased, the encryption system is less prone to be compromised. In one embodiment, a plurality of sets of seed values may be provided, with each set of seed values having a different number of seed values. In one embodiment, depending upon the characteristics of the input word, one of the plurality of sets of seed values are selected. For example, if the input word is a frequently occurring word, then a set of seed values having more number of seed values may be selected. In doing so, the initialization vector used to generate the encrypted data will less likely to repeat, thereby minimizing potential compromise of the system.

As an example, let us consider a first set of seed values having eight seed values and a second set of seed values having more number of seed values, for example, sixteen seed values. If the input word is a frequently occurring word like “the”, if a seed value from the first set of seed values is used, there will be eight different possible encrypted data patterns for the input word “the”. However, if a seed value from the second set of seed values is used, there will be sixteen different possible encrypted data pattern for input word “the”. As one skilled in the art appreciates, use of the second set of seed values for a frequently occurring input word will improve the robustness of the encryption system for possible compromise as compared to the use of the first set of seed values.

In one embodiment, the encryption system may maintain a list containing frequently occurring input words. The received input word is compared against this list and if the input word is listed, then a set of seed values having more seed values may be selected. In some embodiments, a threshold value may be set for frequency of occurrence. If the input word has a frequency of occurrence greater than the threshold value, then, a set of seed values having more seed values may be selected. In some embodiments, the data going through the anonymization system may be used to determine a frequency of occurrence for various words. Then, based on a threshold value, appropriate set of seed values may be selected. As one skilled in the art appreciates, the selection of a set of seed values from a plurality of set of seed values may be made based on other criteria including using different tiers of frequency of occurrence of the input word etc.

In some embodiments, it may be desirable to use a large number of initialization vectors, for example, by using a large number of seed values. As previously indicated, to perform functions like search, there is a need to generate corresponding encrypted search key words using all of the initialization vectors. In some embodiments, using large number of initialization vectors may be preferred, for example, to provide increased protection against compromising the encryption system. However, as the number of initialization vector increases, corresponding number of encrypted search key words have to be generated to retrieve corresponding encrypted data. In some embodiments, this may be less preferred, for example, due to increased network traffic.

Now referring to FIG. 7D, exemplary data fields that may be used in yet another embodiment is described. The data fields may include field 750 to store seed value ID used to generate the corresponding anonymized data stored in field 752. In some embodiments, field 754 may be used to store order indicator data that is indicative of the order of the clear data that corresponds to the anonymized data. As an example, each of the clear data “axx”, “bxx” and “cxx” would have a corresponding order indicator data whose value will be such that they preserve (or indicate) the order of the clear data “axx”, “bxx” and “cxx”. For example, if a sort command was issued to manipulate the corresponding anonymized data for “axx”, “bxx” and “cxx” in an ascending order, the value of the corresponding order indicator data will be such that the value of the order indicator data for “axx” will be lower than the value of the order indicator data for “bxx”, which will be lower than the value of the order indicator data for “cxx”. Order indicator data may be sometimes interchangeably referred to as an order ID.

FIG. 7E shows an exemplary table 760, with column 762 showing clear data, column 764 showing corresponding order indicator data for the clear data, column 766 showing the seed value ID and column 768 showing anonymized data that corresponds to the clear data, generated based on the seed value ID. For example, referring to row 769, for clear data “bxx”, the corresponding order ID is a binary value of “10”, the seed value ID is SVID-2 and corresponding anonymized data is “enl”. As one skilled in the art appreciates, in this example, the order ID value for clear data “axx” is a binary value of “01”, which is less than the order ID value for clear data “bxx” which is a binary value of “10”. Further, the order ID value for clear data “bxx” is less than the order ID value for “cxx”, which is a binary value of “11”.

As one skilled in the art appreciates, referring back to table 760, the anonymized data that corresponds to the clear data need not have to maintain its order with reference to other anonymized data. For example, the value of clear data “axx” is lower than the value of clear data “bxx”. However, the value of the corresponding anonymized data do not maintain the same order. As an example, for clear data “axx”, the corresponding value of anonymized data “pkq” is higher than the value of the anonymized data “enl” that corresponds to the clear data “bxx”.

The order ID value for the clear data may be generated using one or more order preserving anonymization techniques. Now, referring to FIG. 7F, an exemplary order indicator generator 770 is described. The order indicator generator 770 may be part of the anonymization system 402. The order indicator generator 770 may be configured to generate the order ID 774 for the clear data. For example, input data 714 as clear data is received by the order indicator generator 770. The order indicator generator 770 may have one or more OID logics which may be configured to generate order ID 774 for the clear data using various techniques.

For example, sortable token anonymization as previously discussed may be used to generate a token that is indicative of the order of the clear data. For example, by creating an ordered tree that corresponds to the order of the clear data and assigning a value to each of the nodes. The node value may be designated as a token to indicate the order of the clear data. The generated token is designated as the order ID for the corresponding clear data. As an example, OID logic 772-1 may be configured to generate tokens that are designated as the order ID for the corresponding clear data.

In yet another embodiment, an order preserving hash may be generated by hashing the clear data with an order preserving hash function. The generated hash is designated as the order ID for the corresponding clear data. In some embodiments, the order ID value may be used only for determining the order of the encrypted data. In such embodiments, it may be preferable to use a one-way hash function to generate an order preserving hash that is indicative of the order of the clear data. In this embodiment, as one-way hash function is used, the generated hash which is used as the order indicator data cannot be used to recreate the clear data. As an example, OID logic 772-2 may be configured to generate order preserving hash by hashing the clear data with an order preserving hash function. The generated order preserving hash is designated as the order ID for the corresponding clear data.

In yet another embodiment, one or more of order preserving encryption techniques may be used to generate the order ID for the clear data. As an example, OID logic 772-3 may be configured as a crypto module to generate order preserving encrypted data, based on the clear data and one or more encryption algorithms. The generated encrypted data may be designated as the order ID for the corresponding clear data.

In some embodiments, based on the anonymization technique used, the anonymized data may include more number of characters or bits than the corresponding clear data. This may be sometimes referred to as expansion. When a search request is sent to retrieve corresponding anonymized data, the search key word that corresponds to the anonymized data will also be subject to expansion, thereby resulting in a longer (i.e. more number of bits or characters) search key than the corresponding search key in clear data. In yet another embodiments, as the number of seed values used to generate data encryption key increases, as previously indicated, there is a need to generate corresponding number of anonymized search keys when a search request is sent to retrieve anonymized data that corresponds to the search request. Now, yet another alternate embodiment of anonymization technique will be described, to provide improved search capability of anonymized data.

In one embodiment, a cross reference between the clear data and a portion of the anonymized data is maintained in a data store. FIG. 7G shows an exemplary table 780, with column 782 showing clear data, column 784 showing corresponding generated anonymized data and column 786 showing portion of the anonymized data. For example, referring to row 788, clear data “abcdef” when anonymized, converts to an anonymized data of “412132423”. A portion of the anonymized data may be designated as a search ID field. For example, last three characters of the anonymized data may be designated as a search ID field. The data contained in the search ID field may be sometimes referred to as a search ID. Now referring back to row 788, the search ID field of the anonymized data “412132423” has a search ID of “423”. The search ID of “423” is cross referenced with the corresponding clear data. Now referring to row 790, clear data “abcdef” when anonymized, converts to an anonymized data of “451431932”, which is different than the anonymized data that is shown in row 788. As previously articulated, for same clear data, the corresponding anonymized data may be different, based upon the seed value used during the anonymization. Based on the anonymized data of “451431932”, the corresponding search ID will be “932”. The search ID of “932” is cross referenced with the corresponding clear data.

Now, referring to FIG. 7H, an exemplary table 790 that may be constructed and stored in a data store, based on the data shown in FIG. 7G is described. The data store may be part of the anonymization system 402. In some embodiments, the data store may be part of the token vault 414. In this example, each clear data is assumed to consist of two portions, with each portion consisting of three letters. For example clear data in row 788 consists of two portions “abc” and “def”. Further, it is possible that search requests may be generated for each of the portions independently. In some embodiments, each portion may represent a word. In this example, each portion is referred to as a search key. For example, referring to table 790, column 792 shows various search keys and column 794 shows various corresponding search IDs.

As an example, referring to row 793-1, for search key “abc”, the corresponding search IDs are “423”, “213” and “952”. Now, referring to row 793-2, for search key “ghi”, the corresponding search IDs are “213”, 479″ and “510”. Similarly, referring to row 793-3, for search key “kah”, the corresponding search ID is “542”. As one skilled in the art appreciates, there may be a plurality of search ID for same search key.

When a search request is received with a search term in clear data form, corresponding search key is identified from the search term. Then, one or more search IDs that correspond to the identified search key is retrieved. A search request query is formed using the retrieved search IDs as the keys to search the anonymized data. The retrieved search IDs are compared against data contained in the search ID field of the anonymized data. For example, if the last three characters of the anonymized data is designated as the search ID field, the retrieved search IDs are compared with the last three characters of the anonymized data for a match. All anonymized data with a match are retrieved as part of the response to the search request. The retrieved anonymized data is then de-anonymized to generate corresponding clear data.

For example, in some embodiments, seed value IDs corresponding to each of the anonymized data is used to determine their corresponding data encryption key that was used to anonymize the clear data. In some embodiments, the de-anonymized data is then compared with the search key in clear data form and only those de-anonymized data that match with the search key is returned as a response to the received search request. De-anonymized data that do not match with search key in clear data form may be discarded.

In some embodiments, one or more indicia may be used to identify the search ID field of the anonymized data. For example, one or more special characters may be used as an indicia to indicate the beginning of the search ID field. For example, one or more special characters may be inserted in the anonymized data, prior to the beginning of the search ID field. For example, the indicia to indicate the beginning of the search ID field may be referred to as a search ID field marker. In some embodiments, the search ID field marker may be characters or symbols that may be recognized as word breaks. Some possible characters may be a “space”, “semi-colon”, “comma” or a “period” etc.

As one skilled in the art appreciates, during de-anonymization of the anonymized data, the characters that correspond to the search ID field marker are ignored or deleted from the retrieved anonymized data. In some embodiments, search ID field marker may be prepended to the search ID so that any match of the search ID with the corresponding anonymized data will occur with anonymized data contained in the search ID field of the anonymized data. FIG. 7J shows an exemplary anonymized data 752 with a search ID field marker 796 and search ID field 798. For example, the data contained in the search ID field 798 may correspond to the search ID field data shown in column 786 of table 780 of FIG. 7F.

Now, referring to FIG. 7H, if the table 790 is corrupted or is not accessible for any reason, the table 790 may be recreated by retrieving the anonymized data from the destination computing device and de-anonymizing the anonymized data to generate corresponding clear data. Search key may be retrieved from the de-anonymized clear data and corresponding search ID may be retrieved from the search ID field of the anonymized data. In some embodiments, capability to recreate table 790 from the anonymized data may be a desirable feature.

As one skilled in the art appreciates, one or more fields of data indicative of the type of anonymization performed and/or containing variables needed to de-anonymize the anonymized data may be transmitted to the destination computing device, along with the anonymized data. One or more of these fields may be used during the de-anonymization of the anonymized data. As an example, the seed value ID is one such variable.

In some embodiments, a check code may be generated using one or more fields of data being transmitted to the destination computing device. The generated check code may also be sent along with anonymized data. The check code may be a checksum or the like. Upon retrieving the anonymized data from the destination computing device, another check code is generated and checked against the received check code to confirm received data is not corrupted or modified and the like.

In some examples, it may be desirable to maintain same number of characters in the anonymized data as its corresponding clear data. For convenience, such an anonymization technique may be sometimes referred to as length preserving anonymization or LPA for short. In some examples, such an anonymization technique may be sometimes referred to as length preserving encryption or LPE for short.

In some examples, input data may be numbers with specific characteristics, for example, whole number, fractional numbers, positive numbers and negative numbers. And anonymized output data may have to have same characteristics. Depending upon the application, numbers may be stored in different numeric data types. For example, short integers, long integers, single precision floating point numbers (sometimes referred to as floats) and double precision floating point numbers (sometimes referred to as doubles) data types. Choice of data types are driven by various considerations, including allocated storage space, type of number (positive number, negative number, numbers with fractions) etc.

Precision is the total number of digits that can be held in a field. For example, the number “123456” has a precision of 6. Scale is the number of decimal places that can be stored in the field. For example, a number like 123456.789 has a precision of 8 and scale of 3. Integers are going to hold whole numbers and may be classified as a short integer or a long integer. For example, a short integer may have a lower predefined precision than a long integer, both driven by the allocation of number of bytes of storage to the field, for example, in a computing system or an application. Let us presume, the preset threshold in an application for a short integer is a precision of 5. As an example, a short integer with a precision of 5 can hold numbers from 0 to +99,999. If we need to have both positive and negative integers, we need one additional digit. So, a long integer with a precision of 6 can hold numbers from −99,999 to +99,999. However, a short integer with a precision of 5 can hold numbers from −9,999 to +9,999.

Single precision floating point numbers and double precision floating point numbers have three portions, a sign portion, an exponent portion and a significand precision portion. Generally, 32 bits are allocated for a single precision floating point storage and 64 bits are allocated for a double precision floating point storage out of which one bit is allocated as sign bit. In single precision floating point number, exponent portion will be assigned 8 bits and significand precision portion will be assigned 23 bits, for a total of 32 bits. In double precision floating point number, exponent portion will be assigned 11 bits and significand precision portion will be assigned 52 bits, for a total of 64 bits (with one bit allocated as sign bit). Floating point representations are generally used when the numbers may be large and exceed allocated precision and scale. For example, numbers that cannot be represented as either a short integer or a long integer size limitations.

Exemplary implementation to anonymize numbers, sometimes having predefined constraints to be followed in the anonymized output will now be described.

Now, referring to FIG. 7K, a clear data 744 field, a modified clear data 746 field and an interim anonymized data 748 field, converted interim anonymized data 749 and interim clear data 745 field is shown. The clear data 744 field may represent a number, for example, a short integer. The clear data 744 may be a number represented in a first base encoding scheme. For example, clear data 744 may be a number 8517, which is represented in a Base 10 encoding scheme. In one example, the clear data 744 is converted to a modified clear 746 data represented in a second base encoding scheme. For example, the number 8517 may be converted to a modified clear data 746 in a Base 2 encoding scheme. i.e., converting the number 8517 to a binary number. So, the modified clear data 746 in this example will be a binary string of “0010000101000101”, with most significant bit (MSB) “0” indicative of the sign of the number, here a positive sign. This modified clear data 746 is then anonymized, for example, using a length preserving anonymization, to derive an interim anonymized data 748. For example, the binary string of “0010000101000101” is anonymized to derive an interim anonymized data 748, for example, a binary string of “1010110110001101”. This binary string is now converted to an interim converted anonymized data 749 in the first base encoding scheme, which in this example is a base 10 encoding. When the binary string “1010110110001101” is converted to a base 10 encoding, the resulting number is −21107, which will be the converted interim anonymized data 749. The converted interim anonymized data will be designated as the anonymized data, if the converted interim anonymized data meets the predefined characteristics of the clear data.

Let us presume, the clear data is defined to be an integer with a precision of 6 and permits both positive and negative integers. As one skilled in the art appreciates, the clear data was four digits and the anonymized data has 6 digits (including the sign digit). As both positive and negative integers are permitted and the converted interim anonymized data of −21107 has 6 digits (including the sign digit), it meets the predefined characteristics of the clear data. Therefore, the converted interim anonymized data is designated as anonymized data. The anonymized data is transmitted to the destination computing device.

In some examples, the precision of the clear data may be set to 6, however, the clear data may be designated as a positive integer. In such an example, the converted interim anonymized data of −21107 although meets the precision criteria set for the clear data, it does not meet the positive integer criteria of the clear data. In such a situation, the interim anonymized data 748 is once again anonymized to derive another interim anonymized data, for example, a second interim anonymized data. This second interim anonymized data 748, for example, may be a binary string of “0010110110101101”. This binary string is now converted to a converted interim anonymized data 749 in the first base encoding scheme, which in this example is a base 10 encoding. When the binary string “0010110110101101” is converted to a base 10 encoding, the resulting number is 11693, with MSB indicative of a positive number. The converted interim anonymized data of 11693 has a precision of 6 and is a positive number, which meets the predefined characteristics of the clear data. Now, the converted interim anonymized data will be designated as anonymized data. The anonymized data of 11693 is transmitted to the destination computing device.

If on the other hand, upon anonymization of the second interim anonymized data and the resulting converted interim anonymized data is a negative number, the second interim anonymized data is again anonymized, until the resulting converted interim anonymized data meets the predefined characteristics of the clear data. In this example, until the interim anonymized data is a positive number.

In some examples, the clear data may have to be within a specified range, with a lower bound value and an upper bound value. For example, the clear data may be a positive integer, within a range of lower bound value of 100 and an upper bound value of 10,100, giving a range of 10,000. Let us assume, the clear data value is 420. First, the clear data is normalized to a preset lower bound value. As an example, the preset lower bound value may be zero, providing an offset value of 100, between the preset lower bound value of 100 and the lower bound value of zero. In this example, the offset value of 100 is subtracted from the clear data value of 420, to arrive at a normalized clear data value of 320. The normalized clear data value of 320 is now converted to a modified clear data in a second base encoding scheme, for example, base 2 encoding.

As one skilled in the art appreciates, a range value of 10,000 for the clear data may be represented using fourteen bits. With an additional sign bit, total number of bits needed will be fifteen. If the clear data field is defined to be 16 bits, we will have two most significant bits of “00” to represent binary numbers within a range of 10000. Using this example, the normalized clear data of 320 is converted to a modified clear data of “00000101000000”. The modified clear data of “00000101000000” is anonymized to derive an interim anonymized data. For example, the interim anonymized data may be “0001001000110011”. Converting the interim anonymized data of “0001001000110011” to a base 10 value, we get a value of 9267. To this value, the offset of 100 is added, to get a value of 9367. The converted interim anonymized data (after adding the offset value) has a value of 9267, which is within the specified range of value of 100 to 10,100. Therefore, the converted interim anonymized data with a value of 9367 is designated as the anonymized data. The anonymized data is transmitted to destination computing device, over a network.

If in the above example, the interim anonymization data was say, “0011001000110011”. Converting the interim anonymized data of “0011001000110011” to a base 10 value, we get a value of “25651”. To this value, the offset of 100 is added, to get a value of “25751”. Now, the converted interim anonymized data (after adding the offset value) has a value of “25751”, which is not within the specified range of value of 100 to 10,100.

In such a situation, the interim anonymized data 748 is once again anonymized to derive another interim anonymized data, for example, a second interim anonymized data. This second interim anonymized data 748, for example, may be a binary string of “0000011001010100”. Converting the interim anonymized data “0000011001010100” to a base 10 value, we get a value of “3240” for the second interim converted anonymized data. To this value, the offset of 100 is added, to get a value of “3340”. Now, the converted interim anonymized data (after adding the offset value) is “3340”, which is within the specified range of value of 100 to 10,100. Therefore, the converted interim anonymized data with a value of “3340” is designated as the anonymized data. The anonymized data is transmitted to destination computing device, over a network.

If on the other hand, upon anonymization of the second interim anonymized data and the resulting converted interim anonymized data value after adding the offset value is still not within the specified range, the second interim anonymized data is again anonymized, until the resulting converted interim anonymized data after adding the offset value meets the predefined characteristics of the clear data. In this example, until the interim anonymized data is within the specified range.

Although in the example described above, the offset is added after converting the interim anonymized data to a base 10 value, as one skilled in the art appreciates, a corresponding binary value for the offset may be added to the interim anonymized data in binary value, before converting the result to a base 10 value. In some examples, a normalized range may instead be used to verify if the converted interim anonymized data is within the range. In this example, whether the converted interim anonymized data is within the normalized range of 0-10,000. If the converted interim anonymized data is within the normalized range, before designating the converted interin anonymized data as the anonymized data, the offset value may be added to the converted interim anonymized data. In this example, the offset of 100 is added, before designating the converted interim anonymized data as the anonymized data.

In yet other examples, only a portion of the modified clear data may be anonymized. As an example, to represent a range of 10,000 only fourteen binary bits are sufficient. So, in some embodiments, only fourteen least significant bits of the modified clear data may be anonymized to derive an interim anonymized data. Such an implementation may advantageously generate less number of interim anonymized data that may fall outside the designated range.

In yet another example, the clear data may represent a date in a first format. As an example, in a month, day and year format. Sometimes, clear data may also have associated hours, minutes and seconds. The date represented in the first format is converted to a date represented in a second format. As an example, the date represented in the second format may be an offset from an epoch time. One possible epoch date and time may be unix time 0, which is Jan. 1, 1970 at midnight (UTC/GMT). The offset from the epoch date and time may be represented in seconds or milliseconds elapsed since the predefined epoch date and time.

For example, the clear data may represent a date of Jul. 4, 2013 at midnight GMT, in a month, day and year format. The date may be represented as an offset from the epoch date, for example, unix time 0. This will give the date in a second format, for example, as epoch time stamp of 1372860000 in seconds, which is the offset from the unix time 0, in seconds. In some examples, time stamp may also be represented in millisecond, which in this example will be 137286000000 in milliseconds, which is the offset from the unix time 0, in milliseconds. Depending on the implementation, the offset in seconds or milliseconds may be used as the clear data and converted to the modified clear data, for example, to a binary data.

The modified clear data is then anonymized to derive an interim anonymized data, as previously discussed with other examples. Before designating the converted interim anonymized data as the anonymized data, the date represented as an offset by the interim anonymized data is represented as a date in the first format, for example, in month, day and year format.

In some examples, the interim anonymized data for numbers represented as floats or doubles, could represent “NaN” (not a number). This number does not correspond to any floating or double number in the standard way of converting them into bits for storing in the computing device. For example the following arrangement of bits is an NaN for a floating point number where x is either 0 or 1, for example, arrangement of bits 0111 1111 10xx xxxx xxxx xxxx xxxx xxxx.

During anonymization or deanonymization of the floating point numbers, if the input is NaN, it is left as such. If the input is not NaN, and during anonymization, if any of the interim anonymized values become NaN then it is considered to be out of range and the anonymization or deanonymization process continues till the values are not NaN.

Now, an example system and method to implement various anonymization approaches will now be described. As previously described, anonymization system 402 may be used to implement various anonymization approaches. As another example, various modules described with reference to FIG. 7A may also be used. For example, crypto module 702 may be used to perform the anonymization. For example, one or more logic modules may be provided in the anonymization system 402 or crypto module 702 to perform various conversion, manipulation and comparisons required to implement various examples described in this disclosure. In some embodiments, crypto modules may be configured to perform various conversion, manipulation and comparisons required to implement various examples described in this disclosure. For example crypto 1 module 416 or crypto 2 module 418 of FIG. 4A may be configured to perform various conversion, manipulation and comparisons. As another example, crypto module 702 of FIG. 7A may be configured to perform various conversion, manipulation and comparisons.

As another example, referring to FIG. 7L, a logic module 756 may be provided. The logic module 756 may include various conversion, manipulation and comparison modules. As an example, a conversion module 757, a manipulation module 758 and a comparison module 759 may be provided. Conversion module 757 may be configured to receive data in a first format as input, convert the received data into a second format and provide the converted data as an output. For example, Conversion module 757 may be configured to receive clear data in a first base encoding scheme as an input and provide modified clear data in a second base encoding scheme as an output. In another example, conversion module 757 may be configured to receive clear data representing a date in a first format as an input and provide date in a second format as an output.

Manipulation module 758 may be configured to receive data as an input and manipulate the data and provide manipulated data as an output. In one example, manipulation module 758 may be configured to receive clear data within a lower bound value and an upper bound value. The manipulation module 758 may normalize the clear data to a preset lower bound value, for example, by subtracting an offset between the preset lower bound value and the lower bound value. The normalized clear data is then provided as an output of the manipulation module 758.

Comparison module 759 may be configured to perform comparisons of various characteristics of data. Comparisons may include value comparison, length preservation comparison (for example, if an anonymized data has same number of characters as clear data), sign comparison and the like. For example, in one example, comparison module 759 may be configured to compare the characteristics of a converted interim anonymized data with a predefined characteristics of the clear data and provide a signal indicative of a match or a mismatch in the comparison.

As one skilled in the art appreciates, logic module 756 may be implemented in hardware, software running on a processor or in a combination of hardware and software. In some embodiments, logic module 756 may be part of the anonymization system 402. In some embodiments, logic module 756 may be part of the crypto module, for example, crypto module 702.

The modified clear data 746 and interim anonymized data 748 may be anonymized using one or more anonymization schemes as described in this disclosure. As one example, as previously described with reference to FIG. 7A, modified clear data 746 may be used as the input data 714. Referring to FIG. 7B, a seed value of SV-2 with a seed value ID of SVID-2 may be used to generate an initialization vector IV-2. The initialization vector IV-2 may be used by the crypto module 702 to generate anonymized output data 716. As one skilled in the art appreciates, if a length preserving encryption methodology is used, the number of characters in the anonymized output data 716 will have the same number of characters as input data. The anonymized output data 716 will be designated as the interim anonymized data 748. As previously discussed, the modified clear data 746 and interim anonymized data 748 are in the second base encoding scheme.

The interim anonymized data 748 is then converted to a converted interim anonymized data 749 in first base encoding scheme. For example, conversion module 757 may be used to convert the interim anonymized data 748 to a converted interim anonymized data 749. The characteristics of the converted interim anonymized data 748 is then compared with the predefined characteristics of the clear data 744, for example, using the comparison module 759. Based on the comparison, if the converted interim anonymized data 748 meets the predefined characteristics of the clear data 744, then, the converted interim anonymized data 749 is designated as the anonymized data.

If on the other hand, the converted interim anonymized data 748 does not meet the predefined characteristics of the clear data 744, then, the interim anonymized data 748 is used as the input data 714. Referring to FIG. 7B, a seed value of SV-2 with a seed value ID of SVID-2 may be used to generate an initialization vector IV-2. The initialization vector IV-2 may be used by the crypto module 702 to generate anonymized output data 716. The anonymized output data 716 will be designated as the interim anonymized data 748.

For example, conversion module 757 may be used to convert the interim anonymized data 748 to a converted interim anonymized data 749. The characteristics of the converted interim anonymized data 748 is then compared with the predefined characteristics of the clear data 744, for example, using the comparison module 759. Based on the comparison, if the converted interim anonymized data 748 meets the predefined characteristics of the clear data 744, then, the converted interim anonymized data 749 is designated as the anonymized data. If not, the interim anonymized data 748 is again anonymized until the corresponding converted interim anonymized data 748 meets the predefined characteristics of the clear data 744.

In some embodiments, the seed value ID used to generate the initialization vector is stored along with the anonymized data, for example, as previously described with reference to FIG. 7C. In some embodiments, an order ID 764 may be generated for the clear data and stored with the anonymized data, as previously discussed with reference to FIG. 7D and FIG. 7E. In some embodiments, a fixed initialization vector may also be used to anonymize the input data.

When anonymized output data is retrieved, it may be de-anonymized, as described in this disclosure. In one of the previous examples, a clear data of “8517” was anonymized into an anonymized data “−21107” and stored in a data store in a destination computing device. In this example, the clear data is defined to be an integer with a precision of 6 and permits both positive and negative integers.

The anonymized data “−21107” may be retrieved from the data store. The anonymized data is in a first base encoding scheme (for example, base 10 encoding scheme). The anonymized data “−21107” is then converted to a modified anonymized data in the second base encoding scheme (which in this case was a base 2 encoding scheme). For example, conversion module 757 of logic module 756 may be used to perform the conversion. Upon conversion, the modified anonymized data will be “1010110110001101”.

Additionally, the seed value ID may be retrieved. The seed value ID may be used to fetch the corresponding seed value, in this case, seed value of SV-2. This seed value is used to generate the initialization vector, which will have the same value as the initialization vector IV-2 that was used to encrypt the input data. This generated initialization vector IV-2 is then used to de-anonymize the modified anonymized data. As an example, the modified anonymized output data “1010110110001101” is de-anonymized to derive modified clear data of “0010000101000101”. The modified clear data “0010000101000101” in base 2 encoding is then converted to interim clear data 745 in base 10 encoding, for example, using the conversion module 757 of logic module 756. Upon converting “0010000101000101” in base 2 encoding to base 10 encoding, we get of “8517”. The interim clear data of “8517” is designated as the clear data, if the interim clear data “8517” meets the predefined characteristics of the clear data. In this example, the clear data is defined to be an integer with a precision of 6 and permits both positive and negative integers. As the interim clear data “8517” meets the predefined characteristics of the clear data, the interim clear data “8517” is designated as the clear data.

In some examples, the clear data may have gone through more than one anonymization cycle. In such an example, the anonymized data will go through same number of de-anonymization cycle, before the clear data is derived from the anonymized data. For example, as previously described in another example, where the clear data was designated as a positive number. In that example, the interim anonymized data corresponding to converted interim anonymized data of “−21107” was subjected to one more anonymization cycle, to derive an anonymized data of “11693”. If anonymized data of “11693” was retrieved, it will be subject to two de-anonymization cycles as described above, first de-anonymization cycle yielding an interim clear data of “−21107” which would not meet the predefined characteristics of the clear data and second de-anonymization of data “−21107” yielding an interim clear data “8517” that meets the predefined characteristics of the clear data.

In some examples where the clear data represents a date in first format, the date may be represented in a second format before converting the clear data to the modified clear data. For example, date in first format may be converted to a date represented in a second format by the conversion module 757 of logic module 756. The date represented in the second format is then used as the clear data which is then converted to a modified clear data, as previously discussed. The modified clear data is then anonymized as previously discussed, for example, using the crypto module 702. After anonymization, the output data 716 is then converted to date represented in the first format. For example, output data 716 may be converted to date represented in the first format by the conversion module 757. The date represented in the first format is then designated as the anonymized data. The anonymized data is then stored in a data store at a destination computing device.

During de-anonymization, the anonymized data representing date in the first format is retrieved. The retrieved anonymized data is then converted to date represented in the second format, for example, by the conversion module 757 of logic module 756. Now, the date represented in the second format is converted to a modified anonymized data. The modified anonymized data is then de-anonymized as previously described.

In some examples where the clear data is within a specified range with a lower bound value and an upper bound value, clear data is normalized to a preset lower bound value by subtracting an offset between the preset lower bound value and the lower bound value, before converting the clear data to the modified clear data. For example, the clear data may be normalized to a preset lower bound value by using the manipulation module 758 of logic module 756. For example, the manipulation module 758 may subtract the offset value from the clear data. Upon normalization of the clear data, the normalized clear data is then converted to modified clear data and anonymized, as previously described. For example, the offset value is added to the converted interim anonymized data, before designating the converted interim anonymized data as anonymized data. The anonymized data is then stored in a data store at a destination computing device.

In this example, during de-anonymization, the retrieved anonymized data is first normalized, by subtracting the offset from the value of the anonymized data. For example, the manipulation module 758 may receive the anonymized data, subtract the offset value from the anonymized data and provide the normalized anonymized data as output. The normalized anonymized data is then de-anonymized, as previously described. After de-anonymization, the offset value is added to the interim clear data, before designating the interim clear data as clear data.

Now referring to FIGS. 8A-8C and FIGS. 9A-9C an exemplary anonymization implementation will be described. Referring to FIG. 8A, a screen shot 800 presented on a user computer to open a new account for an application running on a hosted cloud is shown. More specifically, the data field 802 refers to the Account Name and the corresponding data for the Account Name is entered in the form field 804. For example, the Account Name entered is “Test Account 1”.

FIG. 8B shows the “POST” action data as transmitted to the hosted cloud, without anonymization. More specifically, reference numeral 804-1 shows the post data that corresponds to the Account Name. As one skilled in the art appreciates, it is not difficult to ascertain the Account Name as “Test Account 1”.

FIG. 8C shows the “POST” data as transmitted to the host cloud, with an embodiment of the anonymization technique described in this disclosure. More specifically, reference numeral 804-2 shows the anonymized data that corresponds to the Account Name. FIG. 8D shows various parts of the anonymized data.

Referring to FIG. 8D, the anonymized data 804-2 includes two anonymized data fields 804-21 and 804-22. The first data field 804-21 corresponds to the word “Test” and the second data field 804-22 corresponds to the word “Account”. Additionally, the preamble 806 for the first data field is TPF1. The postamble 808 for the first data field is 1TSF. Similarly, the preamble 810 for the second data field is TPF1 and the postamble 812 for the second data field is 1TSF1.

Now, referring to FIG. 9A, a screen shot 900 presented on a user computer to view accounts set up for an application running on a hosted cloud is shown. More specifically, the screen shot 900 shows the list of account names that have been set up, for example, account name 902 referring to Test Account 1 that is received in response to a GET action initiated by the user computer to the application hosted on the hosted cloud.

FIG. 9B shows the HTML code 904 constructed by the application hosted on the hosted cloud in response to the GET action. More specifically, the anonymized values 906 of the account name is returned in the HTML code 904. The anonymized value 906 corresponds to the anonymized data 904-2.

FIG. 9C shows the HTML code 908 constructed after processing the received HTML code 904 from the hosted cloud and de-anonymize the anonymized data field 906. More specifically, the HTML code 908 includes the de-anonymized value as shown in data field 910. The HTML code 908 with de-anonymized value for Account Name data field is sent to the user computer, in response to the GET action initiated by the user computer.

Now, referring to FIG. 10, a method of anonymization of data to be transmitted to a hosted cloud is described. In block S1002, an anonymization strategy for data anonymization is provided. In one embodiment, the anonymization strategy is stored in a anonymization strategy module 406. In one embodiment, a management console module 404 may query applications running on the hosted cloud and present and receive meta data (or data schema, data definitions) of each application. The management console module 404 may present the available anonymization strategies for each data field of the meta data to the user computer. The user may select one or more of the anonymization strategies to be applied to various data fields of the application.

The selected anonymization strategy is stored by the management console module 404 in the anonymization strategy module 406, for later use by other modules of the anonymization system 402. The anonymization strategy may be stored as a table in the anonymization strategy module 406. The anaonymization strategy in one embodiment may include schema definition for data manipulation. An exemplary selected anonymization strategy is described with reference to FIG. 5.

In block S1004 data to be transmitted to a destination is received. In one embodiment, the data to be transmitted to a destination is received by the anonymization system from the user computer.

In block S1006, selective anonymization of data based on anonymization strategy is performed. For example, an anonymization strategy may be selected based on the data field and corresponding anonymization strategy, as shown and described with reference to FIG. 5. An exemplary anonymization of data may be performed, as described with reference to FIGS. 8A-8D.

In block S1008, the anonymized data is transmitted to the destination. In one embodiment, the anonymized data is transmitted to the application running on the hosted cloud. An exemplary transmission of anonymized data was at least described with reference to FIGS. 8A-8D.

In block S1010, the anonymized data is stored in the destination. For example, the anonymized data may be stored in a database coupled to an application server, as shown in FIG. 3.

Now referring to FIG. 11A, an exemplary method of processing a request at the destination is described. In block S1102, a request for the stored anonymized data is received at the destination. For example, as described with reference to FIGS. 9A-9C, a GET action request is received at the application running on a hosted cloud.

In block S1104, the request is executed at the destination to selectively retrieve stored anonymized data. As an example, the application server running on the hosted cloud processes the GET action and retrieve anonymized data corresponding to the GET action from a user computer.

In block S1106, the selectively retrieved stored anonymized data is returned. As an example, the application running on the hosted cloud assembles a response to the GET action and returns the selectively retrieved stored anonymized data, as shown in FIG. 9B.

Now referring to FIG. 11B, an exemplary method or processing a response to a request is described. In block S1108, a selectively retrieved anonymized data is response to a request is received. As an example, a response from the hosted cloud to a GET action is received by the anonymization system 402. The response may be a HTTP response as shown in FIG. 9B.

In block S1110, the retrieved stored anonymized data is de-anonymized. For example, the retrieved anonymized data is evaluated by the de-anonymization module 410. The selective preamble contained in the anonymized data is identified. The de-anonymization module performs the de-anonymization based on the identified preamble and generates the de-anonymized data. An exemplary de-anonymized data is shown in FIG. 9C.

In block S1112, the de-anonymized data is returned in response to the request. For example, an HTTP response as described with reference to FIG. 9C is returned to the user computer.

As it is apparent to one skilled in the art, data transfers from user applications are selectively anonymized using one or more anonymization techniques, based on selected anonymization strategy. The anonymization of data happens transparently to the user application.

Although in some embodiments, anonymization techniques may have be described with reference to encryption of the input word, these techniques may be adapted and practiced using tokenization as well.

Although in this disclosure reference is made to transmitting anonymized data to a hosted cloud or a destination system located at a third party location, the disclosure is not limited to the disclosed embodiments. In some embodiments, anonymized data may be stored in a user cloud itself. The server application may be any type of application, including word processing applications, mail applications and the like.

Although the hosted cloud has been described with one or more servers and databases, these clouds may be implemented with additional servers and databases that may act as redundant systems or cumulative systems.

As one skilled in the art appreciates, various embodiments of this disclosure may provide one or more of the following benefits. For example, anonymization of transmitted data may occur transparent to the user application. Anonymized data may be sortable, based on the selected anonymization strategy. Anonymized data may be searchable, based on the selected anonymization strategy. Anonymized data may be subjected to case-insensitive search, based on the selected anonymization strategy. Portions of a data field may be anonymized, retaining other portion of the data field in its original form. Portions of the data field retained in its original form may be bypassed from the anonymization process and system, which may lead to improved overall performance of the anonymization system.

While embodiments of the present invention are described above with respect to what is currently considered its preferred embodiments, it is to be understood that the invention is not limited to that described above. To the contrary, the invention is intended to cover various modifications and equivalent arrangements within the spirit and scope of the appended claims. 

What is claimed is:
 1. A method for anonymizing data to be transmitted to a destination computing device, comprising: receiving by an anonymization system executed on a computing device, data to be transmitted to the destination computing device from a user computer, the received data including one of a plurality of numbers stored in different data types and defining a clear data in a first base encoding scheme represented as a base(P) encoding, where P is a positive integer, with one or more predefined characteristics, wherein the one or more predefined characteristics is associated with at least a number of precision and a sign digit; converting the clear data to a modified clear data in a second base encoding scheme represented as a base(Q) encoding, where Q is a positive integer and Q is different than P; anonymizing the modified clear data using an anonymization module executed on the anonymization system, to derive an interim anonymized data in the second base encoding scheme based on an anonymization strategy, including at least using an initialization vector; converting the interim anonymized data to a converted interim anonymized data in the first base encoding scheme; comparing the characteristics of the converted interim anonymized data to the predefined characteristics of the clear data for a match; designating the converted interim anonymized data in the first base encoding scheme, as a target anonymized data upon match, otherwise performing one or more anonymization of the interim anonymized data until the converted interim anonymized data matches the predefined characteristics of the clear data; and transmitting the target anonymized data as the anonymized data of the clear data to the destination computing device over a network.
 2. The method of claim 1, wherein the clear data is an integer within a range of integers.
 3. The method of claim 1, further including: wherein the clear data represents a date in a first format; representing the date in a second format before converting the clear data to the modified clear data; and after anonymization, representing the date in the first format.
 4. The method of claim 3, wherein the date in first format is represented at least in a day, month and year format; and the date in second format is represented as an offset from an epoch date.
 5. The method of claim 3, wherein the preset lower bound value is a zero.
 6. The method of claim 1, further including: wherein the clear data is within a specified range with a lower bound value and an upper bound value; normalizing the clear data to a preset lower bound value by subtracting an offset between the preset lower bound value and the lower bound value before converting the clear data to the modified clear data.
 7. The method of claim 6, wherein before designating the converted interim anonymized data as the anonymized data, adding the offset value to the converted interim anonymized data.
 8. The method of claim 1, wherein the anonymized data has the same number of characters as the clear data.
 9. The method of claim 1 wherein anonymizing the modified clear data further including: generating the initialization vector using a seed value; and anonymizing the modified clear data using the generated initialization vector.
 10. The method of claim 9 wherein transmitting the anonymized data further including transmitting a seed value identifier that corresponds to the seed value, to the destination computing device over a network.
 11. The method of claim 9, wherein generating the initialization vector further including: selecting one of a plurality of seed values; designating the selected one of the plurality of seed values as a fixed seed value; and generating the initialization vector using the fixed seed value.
 12. The method of claim 9, further including: retrieving the anonymized data; converting the anonymized data to a modified anonymized data in the second base encoding scheme; regenerating the initialization vector using the seed value; de-anonymizing the modified anonymized data using the regenerated initialization vector to derive the modified clear data; converting the modified clear data to interim clear data in the first base encoding scheme; and designating the interim clear data as the clear data, if interim clear data matches the predefined characteristic of the clear data.
 13. The method of claim 12, wherein, the anonymized data represents date in the first format; representing the date in the second format, before converting the anonymized data to a modified anonymized data in the second base encoding scheme; and before designating interim clear data as clear data, representing the date in the first format.
 14. The method of claim 12, wherein, the anonymized data is within a specified range with a lower bound value and an upper bound value; normalizing the anonymized data to a preset lower bound value by subtracting an offset between the preset lower bound value and the lower bound value, before converting the anonymized data to a modified anonymized data in the second base encoding scheme; and before designating, adding the offset value to the interim clear data.
 15. The method of claim 12, wherein the anonymized data is a float and includes a NaN portion and the NaN portion is not de-anonymized and retained in its original form.
 16. The method of claim 12, wherein the anonymized data is a double and includes a NaN portion and the NaN portion is not de-anonymized and retained in its original form.
 17. The method of claim 9, further including generating an order indicator data indicative of the order of the clear data and transmitting the order indicator data along with the anonymized data to the destination computing device over the network.
 18. The method of claim 17, further including: receiving a request to sort the anonymized data stored at the destination computing device; and sorting the anonymized data based on the corresponding order indicator data.
 19. The method of claim 1, wherein the clear data is a float and includes a NaN portion; and the NaN portion is not anonymized and retained in its original form in the anonymized data.
 20. The method of claim 1, wherein the clear data is a double and includes a NaN portion; and the NaN portion is not anonymized and retained in its original form in the anonymized data.
 21. An anonymization system to anonymize data transmitted to a destination computing device, comprising: an anonymization strategy module of the anonymization system executed on a computing device, the anonymization strategy module configured to store anonymization strategy for data anonymization in a memory storage; a logic to receive data to be transmitted to the destination computing device, from a user computer, the received data including one of a plurality of numbers stored in different data types and defines a clear data in a first base encoding scheme represented as a base(P) encoding, where P is a positive integer, with one or more predefined characteristics, wherein the one or more predefined characteristics is associated with at least a number of precision and a sign digit; a logic to convert the clear data to a modified clear data in a second base encoding scheme represented as a base(Q) encoding, where Q is a positive integer and Q is different than P; and an anonymization module executed on the anonymization system to anonymize the modified clear data based on an anonymization strategy, including at least using an initialization vector, to generate an interim anonymized data in the second base encoding scheme; the anonymization system configured to convert the interim anonymized data to a converted interim anonymization data in the first base encoding scheme; compare the characteristics of the converted interim anonymized data to the predefined characteristics of the clear data for a match; designate the converted interim anonymized data in the first base encoding scheme, as a target anonymized data upon match, otherwise perform one or more anonymization of the interim anonymized data until the converted interim anonymized data matches the predefined characteristics of the clear data; and transmit the target anonymized data as the anonymized data of the clear data to the destination computing device over a network.
 22. The system of claim 21, wherein the clear data is an integer within a range of integers.
 23. The system of claim 21, further including: wherein the clear data represents a date in a first format; the date is represented in a second format before the clear data is converted to the modified clear data; and after anonymization, the date is represented in the first format.
 24. The system of claim 23, wherein the date in first format is represented at least in a day, month and year format; and the date in second format is represented as an offset from an epoch date.
 25. The system of claim 21, further including: wherein the clear data is within a specified range with a lower bound value and an upper bound value; the clear data is normalized to a preset lower bound value by subtracting an offset between the preset lower bound value and the lower bound value before the clear data is converted to the modified clear data.
 26. The system of claim 25, wherein before the converted interim anonymized data is designated as the anonymized data, the offset value is added to the converted interim anonymized data.
 27. The system of claim 25, wherein the preset lower bound value is a zero.
 28. The system of claim 21, wherein the anonymized data has the same number of characters as the clear data.
 29. The system of claim 21 wherein, the initialization vector is generated using a seed value; and the modified clear data is anonymized using the generated initialization vector.
 30. The system of claim 29 wherein, a seed value identifier that corresponds to the seed value is transmitted to the destination computing device over a network.
 31. The system of claim 29, wherein, one of a plurality of seed values is selected; the selected one of the plurality of seed values is designated as a fixed seed value; and the initialization vector is generated using the fixed seed value.
 32. The system of claim 29, further including: the anonymized data is retrieved from the destination computing device; the anonymized data is converted to a modified anonymized data in the second base encoding scheme; the initialization vector is regenerated using the seed value; the modified anonymized data is de-anonymized using the regenerated initialization vector to derive the modified clear data; the modified clear data is converted to interim clear data in the first base encoding scheme; and the interim clear data is designated as the clear data, if interim clear data matches the predefined characteristic of the clear data.
 33. The system of claim 32, wherein, the anonymized data represents date in the first format; the date is represented in the second format, before the anonymized data is converted to a modified anonymized data in the second base encoding scheme; and before interim clear data is designated as clear data, the date is represented in the first format.
 34. The system of claim 32, wherein, the anonymized data is within a specified range with a lower bound value and an upper bound value; the anonymized data is normalized to a preset lower bound value by subtracting an offset between the preset lower bound value and the lower bound value, before the anonymized data is converted to a modified anonymized data in the second base encoding scheme; and before interim clear data is designated as clear data, the offset value is added to the interim clear data.
 35. The system of claim 32, wherein the anonymized data is a float and includes a NaN portion and the NaN portion is not de-anonymized and retained in its original form.
 36. The system of claim 32, wherein the anonymized data is a double and includes a NaN portion and the NaN portion is not de-anonymized and retained in its original form.
 37. The system of claim 29, wherein an order indicator data indicative of the order of the clear data is generated and the order indicator data is transmitted along with the anonymized data to the destination computing device over the network.
 38. The system of claim 37, further including: a request to sort the anonymized data stored at the destination computing device is received; and the anonymized data is sorted based on the corresponding order indicator data.
 39. The system of claim 21, wherein the clear data is a float and includes a NaN portion; and the NaN portion is not anonymized and retained in its original form.
 40. The system of claim 21, wherein the clear data is a double and includes a NaN portion; and the NaN portion is not anonymized and retained in its original form. 